Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d46cc13e5ca3ec5686189cb9dc1c7dcf5a6fe13c74a346c523e93cfb107b04f2

Tx prefix hash: eff7a13baf1f284442f6889f7d0442eb13eddecfe77473e5148e40a905e21f94
Tx public key: 93a65a13e9f87ae2200ca1567e97a25d91951c1f171bd3b4669f2199bf4d136a
Timestamp: 1576047293 Timestamp [UCT]: 2019-12-11 06:54:53 Age [y:d:h:m:s]: 05:166:06:13:56
Block: 25415 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1264501 RingCT/type: yes/0
Extra: 0193a65a13e9f87ae2200ca1567e97a25d91951c1f171bd3b4669f2199bf4d136a0211000000189159db1e000000000000000000

1 output(s) for total of 505.580626506000 dcy

stealth address amount amount idx
00: 0a800372f29b535a5b1111725dabfa4ee63a44a8ac1c278d1feab360bf293de2 505.580626506000 41746 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": 25425, "vin": [ { "gen": { "height": 25415 } } ], "vout": [ { "amount": 505580626506, "target": { "key": "0a800372f29b535a5b1111725dabfa4ee63a44a8ac1c278d1feab360bf293de2" } } ], "extra": [ 1, 147, 166, 90, 19, 233, 248, 122, 226, 32, 12, 161, 86, 126, 151, 162, 93, 145, 149, 28, 31, 23, 27, 211, 180, 102, 159, 33, 153, 191, 77, 19, 106, 2, 17, 0, 0, 0, 24, 145, 89, 219, 30, 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