Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 583fe7ca1f6b6d21feeb2a909617a4c70a59980a733dbd20b5449fe9099ddad8

Tx prefix hash: 0ce0c9750e025815a9059b839d716386d11958bdefc2bba068097e2223a71924
Tx public key: 154922fa3b4b04bf63bb8b42bed8efc7d6df06c42c0c956eb9d85b10e059fbfb
Timestamp: 1581088054 Timestamp [UCT]: 2020-02-07 15:07:34 Age [y:d:h:m:s]: 05:097:00:32:34
Block: 60467 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1221648 RingCT/type: yes/0
Extra: 01154922fa3b4b04bf63bb8b42bed8efc7d6df06c42c0c956eb9d85b10e059fbfb02110000000156c366d3000000000000000000

1 output(s) for total of 386.944382027000 dcy

stealth address amount amount idx
00: 356bc40ca736870300b9a8aa498647905739182e6414acb8438c81f9bac5890b 386.944382027000 111434 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": 60477, "vin": [ { "gen": { "height": 60467 } } ], "vout": [ { "amount": 386944382027, "target": { "key": "356bc40ca736870300b9a8aa498647905739182e6414acb8438c81f9bac5890b" } } ], "extra": [ 1, 21, 73, 34, 250, 59, 75, 4, 191, 99, 187, 139, 66, 190, 216, 239, 199, 214, 223, 6, 196, 44, 12, 149, 110, 185, 216, 91, 16, 224, 89, 251, 251, 2, 17, 0, 0, 0, 1, 86, 195, 102, 211, 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