Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c2ff4e2ad14c8b087f8120eafc5819f92ec2e37c976f6c7dde83ed86d32da087

Tx prefix hash: 0787e79833bad1ea5240f26368124110a0215b5dbec5272364492315a481bc7c
Tx public key: b3a96dbce3d1e0410a64c30a79f447e90720074913809546f9da4b3a5922a5d5
Timestamp: 1580486370 Timestamp [UCT]: 2020-01-31 15:59:30 Age [y:d:h:m:s]: 04:301:06:24:18
Block: 55982 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1106430 RingCT/type: yes/0
Extra: 01b3a96dbce3d1e0410a64c30a79f447e90720074913809546f9da4b3a5922a5d50211000000012264afe6000000000000000000

1 output(s) for total of 400.413968026000 dcy

stealth address amount amount idx
00: c8776ff979d704f238c85fc0eefc7bc4821d811f18ea92088694939464e811da 400.413968026000 103251 of 0

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": 55992, "vin": [ { "gen": { "height": 55982 } } ], "vout": [ { "amount": 400413968026, "target": { "key": "c8776ff979d704f238c85fc0eefc7bc4821d811f18ea92088694939464e811da" } } ], "extra": [ 1, 179, 169, 109, 188, 227, 209, 224, 65, 10, 100, 195, 10, 121, 244, 71, 233, 7, 32, 7, 73, 19, 128, 149, 70, 249, 218, 75, 58, 89, 34, 165, 213, 2, 17, 0, 0, 0, 1, 34, 100, 175, 230, 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