Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e015248acea588fc3877c430b6970c5b20ff298b71d6755b457f0e4a6d79a991

Tx prefix hash: bb3c79dae966440b07b39dca2d4f1c65261f742a33ff96a2bbc4c1a1fa651af5
Tx public key: 094735bfe0a703f9eb4715e67918919e0caaacb383b43533a88c4a10dd3162b7
Timestamp: 1732144746 Timestamp [UCT]: 2024-11-20 23:19:06 Age [y:d:h:m:s]: 00:003:02:17:55
Block: 1158138 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 2225 RingCT/type: yes/0
Extra: 01094735bfe0a703f9eb4715e67918919e0caaacb383b43533a88c4a10dd3162b70211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bceb7d0864b124e9e8caca78c3b4efa70083dcb59a17376e26b83e8ed9a671e0 0.600000000000 1643767 of 15

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": 1158148, "vin": [ { "gen": { "height": 1158138 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bceb7d0864b124e9e8caca78c3b4efa70083dcb59a17376e26b83e8ed9a671e0" } } ], "extra": [ 1, 9, 71, 53, 191, 224, 167, 3, 249, 235, 71, 21, 230, 121, 24, 145, 158, 12, 170, 172, 179, 131, 180, 53, 51, 168, 140, 74, 16, 221, 49, 98, 183, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 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