Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: dd530d0449ef8faed12253b9c5f71865a412d2439ba6bb479ac9cd305e40255c

Tx prefix hash: 9ea73e0e5dbe2d58397b36223293b91941eacfce796dfed9e49833383444202a
Tx public key: 64161a6c58abcff9717f373e07d7dbe082c6a21a722d395b2be0a26d2f2d4cc5
Timestamp: 1719606379 Timestamp [UCT]: 2024-06-28 20:26:19 Age [y:d:h:m:s]: 00:118:20:47:47
Block: 1054277 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 85126 RingCT/type: yes/0
Extra: 0164161a6c58abcff9717f373e07d7dbe082c6a21a722d395b2be0a26d2f2d4cc50211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0b96c44ab81983abd5ca7fb21e591f33bc8eb02b4031bbd54f4632f8789a47bc 0.600000000000 1524638 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 1054287, "vin": [ { "gen": { "height": 1054277 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0b96c44ab81983abd5ca7fb21e591f33bc8eb02b4031bbd54f4632f8789a47bc" } } ], "extra": [ 1, 100, 22, 26, 108, 88, 171, 207, 249, 113, 127, 55, 62, 7, 215, 219, 224, 130, 198, 162, 26, 114, 45, 57, 91, 43, 224, 162, 109, 47, 45, 76, 197, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8