Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 55d7d627fa79b2f4c355bccb1882632e4e845ac3e62f6dbe8bf121514f2f1167

Tx prefix hash: 7d06097b441b656ee335709e502d2c234fa1985a386c310daff5399b0e0c353a
Tx public key: 9d4ff4121e0232057b46a62250c2dd4210164f2a5da8e58a8d9ad2ae702af439
Timestamp: 1673469718 Timestamp [UCT]: 2023-01-11 20:41:58 Age [y:d:h:m:s]: 02:300:14:21:33
Block: 672658 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 734227 RingCT/type: yes/0
Extra: 019d4ff4121e0232057b46a62250c2dd4210164f2a5da8e58a8d9ad2ae702af43902110000000252542ceb000000000000000000

1 output(s) for total of 3.624138328000 dcy

stealth address amount amount idx
00: b49f60ec891ba339b0a52cb39a7870e25746451852a6d4f307dc378f1eda04d4 3.624138328000 1114221 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": 672668, "vin": [ { "gen": { "height": 672658 } } ], "vout": [ { "amount": 3624138328, "target": { "key": "b49f60ec891ba339b0a52cb39a7870e25746451852a6d4f307dc378f1eda04d4" } } ], "extra": [ 1, 157, 79, 244, 18, 30, 2, 50, 5, 123, 70, 166, 34, 80, 194, 221, 66, 16, 22, 79, 42, 93, 168, 229, 138, 141, 154, 210, 174, 112, 42, 244, 57, 2, 17, 0, 0, 0, 2, 82, 84, 44, 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