Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 13f8a6da10d0b939e6ed8ae5a3f31fe686fdca1489bbd8e01aa5e6b16d6a8c8f

Tx prefix hash: 28d923fb6bab98cf913165d92b43cb3f9510bd2fce89693cba23cd52597779ff
Tx public key: 0545215feabd2d33f8327ebd755c359dc1a52a67bce7319e2d4489b743eb4d0d
Timestamp: 1663843658 Timestamp [UCT]: 2022-09-22 10:47:38 Age [y:d:h:m:s]: 02:179:11:56:46
Block: 593326 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 649685 RingCT/type: yes/0
Extra: 010545215feabd2d33f8327ebd755c359dc1a52a67bce7319e2d4489b743eb4d0d02110000000633af99f4000000000000000000

1 output(s) for total of 6.638420066000 dcy

stealth address amount amount idx
00: 2f0d62e73a1c45d30b65f8dd11509dfe1bda29d7d02740f0ad1a8803f925d1b8 6.638420066000 1028101 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": 593336, "vin": [ { "gen": { "height": 593326 } } ], "vout": [ { "amount": 6638420066, "target": { "key": "2f0d62e73a1c45d30b65f8dd11509dfe1bda29d7d02740f0ad1a8803f925d1b8" } } ], "extra": [ 1, 5, 69, 33, 95, 234, 189, 45, 51, 248, 50, 126, 189, 117, 92, 53, 157, 193, 165, 42, 103, 188, 231, 49, 158, 45, 68, 137, 183, 67, 235, 77, 13, 2, 17, 0, 0, 0, 6, 51, 175, 153, 244, 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