Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 531b5d3667ef4305a7d6e47689f5f32b1cffe32aa117cdd371683bf3911ffdb5

Tx prefix hash: fc4b93e89ae4f1a4db3bd6ef7ce5879da74e7648064070eae734e7c9dd5d8554
Tx public key: 808a69ca494307cca3171097749ff4da5d771313b3a2d47bb3c4b4efa9a92c69
Timestamp: 1578881712 Timestamp [UCT]: 2020-01-13 02:15:12 Age [y:d:h:m:s]: 05:293:20:20:47
Block: 44297 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1357933 RingCT/type: yes/0
Extra: 01808a69ca494307cca3171097749ff4da5d771313b3a2d47bb3c4b4efa9a92c6902110000000f4943cd9f000000000000000000

1 output(s) for total of 437.750339705000 dcy

stealth address amount amount idx
00: e18aa17517da07f723d4dfdf81334420cbad90d8665cd8dc669f431f405af398 437.750339705000 80578 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": 44307, "vin": [ { "gen": { "height": 44297 } } ], "vout": [ { "amount": 437750339705, "target": { "key": "e18aa17517da07f723d4dfdf81334420cbad90d8665cd8dc669f431f405af398" } } ], "extra": [ 1, 128, 138, 105, 202, 73, 67, 7, 204, 163, 23, 16, 151, 116, 159, 244, 218, 93, 119, 19, 19, 179, 162, 212, 123, 179, 196, 180, 239, 169, 169, 44, 105, 2, 17, 0, 0, 0, 15, 73, 67, 205, 159, 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