Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: eb344a4d124db4f09f40e5364193a7124c840b8eaeaa14c73c80af1fd458949c

Tx prefix hash: 9c1ca202450e0b306fba8fb9fad167a7bb75b392359943a33fbbe1447f9d4f9a
Tx public key: cf0fb8d576ef15c1bdf0e910096b70e02da78d8be6d9432b05e1c3c85e052061
Timestamp: 1704178405 Timestamp [UCT]: 2024-01-02 06:53:25 Age [y:d:h:m:s]: 01:130:12:19:09
Block: 926372 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 354418 RingCT/type: yes/0
Extra: 01cf0fb8d576ef15c1bdf0e910096b70e02da78d8be6d9432b05e1c3c85e05206102110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 055972152f0556580cf134653ec96042926f96985aa539903324290d875d93bc 0.600000000000 1384154 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": 926382, "vin": [ { "gen": { "height": 926372 } } ], "vout": [ { "amount": 600000000, "target": { "key": "055972152f0556580cf134653ec96042926f96985aa539903324290d875d93bc" } } ], "extra": [ 1, 207, 15, 184, 213, 118, 239, 21, 193, 189, 240, 233, 16, 9, 107, 112, 224, 45, 167, 141, 139, 230, 217, 67, 43, 5, 225, 195, 200, 94, 5, 32, 97, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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