Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d4d0318873b6179b79e7ae2d2b4ad5f97ce2ef43e0cbf7e61fdcc1b2d58b248b

Tx prefix hash: eeb841df96634b18e3183583a2543b252a7c0bb4e10916265b10cf12e717a146
Tx public key: c4fbc7dc6bf28bcf951159e265f445d1cb2dcbfffbf79915a68bde4ce28abdc5
Timestamp: 1659080782 Timestamp [UCT]: 2022-07-29 07:46:22 Age [y:d:h:m:s]: 02:200:06:58:05
Block: 554114 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 664320 RingCT/type: yes/0
Extra: 01c4fbc7dc6bf28bcf951159e265f445d1cb2dcbfffbf79915a68bde4ce28abdc5021100000007d834ebe0000000000000000000

1 output(s) for total of 8.953450163000 dcy

stealth address amount amount idx
00: 64b7b7bb1db7956aee16591149be39f6c45c831df5d4739cfecd54e8919a1d5c 8.953450163000 985948 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": 554124, "vin": [ { "gen": { "height": 554114 } } ], "vout": [ { "amount": 8953450163, "target": { "key": "64b7b7bb1db7956aee16591149be39f6c45c831df5d4739cfecd54e8919a1d5c" } } ], "extra": [ 1, 196, 251, 199, 220, 107, 242, 139, 207, 149, 17, 89, 226, 101, 244, 69, 209, 203, 45, 203, 255, 251, 247, 153, 21, 166, 139, 222, 76, 226, 138, 189, 197, 2, 17, 0, 0, 0, 7, 216, 52, 235, 224, 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