Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: aecaaa2ab7cf5209c07edda59258ee805eebaa80994e57d0a266cdb2e2ac3384

Tx prefix hash: b3c0d855e799708e124999d8f15a91542e4d57806c46ae39336d524132d868c5
Tx public key: bde083f4ab8eae7f96a7f9c0c5dc1af854893467ffc500f0527c5e16f15e3208
Timestamp: 1577611598 Timestamp [UCT]: 2019-12-29 09:26:38 Age [y:d:h:m:s]: 05:154:15:38:38
Block: 34224 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1260345 RingCT/type: yes/0
Extra: 01bde083f4ab8eae7f96a7f9c0c5dc1af854893467ffc500f0527c5e16f15e32080211000000164ac5aa02000000000000000000

1 output(s) for total of 472.718432666000 dcy

stealth address amount amount idx
00: 4129309a10045b31ddd78d66b0fb8b1b851f6330c03b2f654672b22e8fa7eb00 472.718432666000 57594 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": 34234, "vin": [ { "gen": { "height": 34224 } } ], "vout": [ { "amount": 472718432666, "target": { "key": "4129309a10045b31ddd78d66b0fb8b1b851f6330c03b2f654672b22e8fa7eb00" } } ], "extra": [ 1, 189, 224, 131, 244, 171, 142, 174, 127, 150, 167, 249, 192, 197, 220, 26, 248, 84, 137, 52, 103, 255, 197, 0, 240, 82, 124, 94, 22, 241, 94, 50, 8, 2, 17, 0, 0, 0, 22, 74, 197, 170, 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