Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2447c61051b3ab7cb72debe964f03de9fc6732a5da01ca6ff03c08e3579a937e

Tx prefix hash: 50fa1ed33a5843175608776c58578e523af3420101fbd3fd0217f0afd25fadc7
Tx public key: b94cfcc4a31db568aadcb61c55c4ee1611e887c9a5830213eda11e6bb3bc4a8b
Timestamp: 1711130890 Timestamp [UCT]: 2024-03-22 18:08:10 Age [y:d:h:m:s]: 00:364:05:47:42
Block: 984047 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 260407 RingCT/type: yes/0
Extra: 01b94cfcc4a31db568aadcb61c55c4ee1611e887c9a5830213eda11e6bb3bc4a8b02110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6fede0938f8a5de6a365ef816eaf3a56fc6696f0b9a7c9860fb61d0aa66a71c6 0.600000000000 1444202 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": 984057, "vin": [ { "gen": { "height": 984047 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6fede0938f8a5de6a365ef816eaf3a56fc6696f0b9a7c9860fb61d0aa66a71c6" } } ], "extra": [ 1, 185, 76, 252, 196, 163, 29, 181, 104, 170, 220, 182, 28, 85, 196, 238, 22, 17, 232, 135, 201, 165, 131, 2, 19, 237, 161, 30, 107, 179, 188, 74, 139, 2, 17, 0, 0, 0, 2, 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