Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9cf28955f61986479b1f5543c49189999431900d2157d884dc495548c045c3d3

Tx prefix hash: b500b7cff28ac3d9425aa3e1fad17bb3af7d5f1ab87f088e556a860961c2160e
Tx public key: 4134e4a4a68b7c2f7ed267e80e8a6bfe4b8217edbe344e8c61492c9ab88135a5
Timestamp: 1730489947 Timestamp [UCT]: 2024-11-01 19:39:07 Age [y:d:h:m:s]: 00:146:08:08:25
Block: 1144426 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 104425 RingCT/type: yes/0
Extra: 014134e4a4a68b7c2f7ed267e80e8a6bfe4b8217edbe344e8c61492c9ab88135a5021100000006007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9bb535b9887d511b3e5297d66e7e493919946fa5006ed881c2591b673cc83d61 0.600000000000 1628647 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": 1144436, "vin": [ { "gen": { "height": 1144426 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9bb535b9887d511b3e5297d66e7e493919946fa5006ed881c2591b673cc83d61" } } ], "extra": [ 1, 65, 52, 228, 164, 166, 139, 124, 47, 126, 210, 103, 232, 14, 138, 107, 254, 75, 130, 23, 237, 190, 52, 78, 140, 97, 73, 44, 154, 184, 129, 53, 165, 2, 17, 0, 0, 0, 6, 0, 127, 151, 138, 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