Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 560ec6aba72c52c4b3a5c186d350fe9cb865e02f5522e63013ed1043693f2aaf

Tx prefix hash: 36b750367856d279c42964a5c290e5ae0792968bbe4f993b78d05af837e40f36
Tx public key: 17f6cf86d0e456857fb53e273a2148a2b18f7c7d1a8f196736dff55087d6fdf8
Timestamp: 1577719130 Timestamp [UCT]: 2019-12-30 15:18:50 Age [y:d:h:m:s]: 05:109:07:38:36
Block: 35117 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1227898 RingCT/type: yes/0
Extra: 0117f6cf86d0e456857fb53e273a2148a2b18f7c7d1a8f196736dff55087d6fdf80211000000048a2ee0d9000000000000000000

1 output(s) for total of 469.508712833000 dcy

stealth address amount amount idx
00: f114ec4a31e561b4304a03c344e6e719cf593a178bc3d9a05e7a8235a37f5990 469.508712833000 59158 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": 35127, "vin": [ { "gen": { "height": 35117 } } ], "vout": [ { "amount": 469508712833, "target": { "key": "f114ec4a31e561b4304a03c344e6e719cf593a178bc3d9a05e7a8235a37f5990" } } ], "extra": [ 1, 23, 246, 207, 134, 208, 228, 86, 133, 127, 181, 62, 39, 58, 33, 72, 162, 177, 143, 124, 125, 26, 143, 25, 103, 54, 223, 245, 80, 135, 214, 253, 248, 2, 17, 0, 0, 0, 4, 138, 46, 224, 217, 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