Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d53d17f5f45a86962427541a31c45ab0d587cfbf7f52782bf4877f546bd0e891

Tx prefix hash: 02e6fdc9ddff8bca41e279992e8b42632045506df6cf6237397fceecf86fbc62
Tx public key: 28f8fdc6e88d275e62164cd6ce6a09ea1bb31aed5372d26570ed25f0a1fb66ed
Timestamp: 1673462425 Timestamp [UCT]: 2023-01-11 18:40:25 Age [y:d:h:m:s]: 02:300:13:33:19
Block: 672591 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 734217 RingCT/type: yes/0
Extra: 0128f8fdc6e88d275e62164cd6ce6a09ea1bb31aed5372d26570ed25f0a1fb66ed0211000000048b7b6602000000000000000000

1 output(s) for total of 3.625991358000 dcy

stealth address amount amount idx
00: 4a7dee93aee0e451a0850a319be8b021076c2dcb794a4e01f3431d8e2d40eb25 3.625991358000 1114152 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": 672601, "vin": [ { "gen": { "height": 672591 } } ], "vout": [ { "amount": 3625991358, "target": { "key": "4a7dee93aee0e451a0850a319be8b021076c2dcb794a4e01f3431d8e2d40eb25" } } ], "extra": [ 1, 40, 248, 253, 198, 232, 141, 39, 94, 98, 22, 76, 214, 206, 106, 9, 234, 27, 179, 26, 237, 83, 114, 210, 101, 112, 237, 37, 240, 161, 251, 102, 237, 2, 17, 0, 0, 0, 4, 139, 123, 102, 2, 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