Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 896d6be435caa114045e20dd1d0817fa9eae9fddb2321ad70db4242e7dbe537c

Tx prefix hash: 54e675667d23d5fd7d54bd869c4bc4a04ab9fb814ff654a3356f0b6d841934c8
Tx public key: 93c537030f042130c6ca998e32035b5003e233b5fb5aa9e0b7be6872a9b26e83
Timestamp: 1648460116 Timestamp [UCT]: 2022-03-28 09:35:16 Age [y:d:h:m:s]: 03:217:16:38:15
Block: 468126 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 933499 RingCT/type: yes/0
Extra: 0193c537030f042130c6ca998e32035b5003e233b5fb5aa9e0b7be6872a9b26e830211000000054a0f5013000000000000000000

1 output(s) for total of 17.254583712000 dcy

stealth address amount amount idx
00: 6fc67d2e0fabf824cafc8505bf4d1e3e87071d5c1b71cf19239f0f8c4dee3f2f 17.254583712000 886774 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": 468136, "vin": [ { "gen": { "height": 468126 } } ], "vout": [ { "amount": 17254583712, "target": { "key": "6fc67d2e0fabf824cafc8505bf4d1e3e87071d5c1b71cf19239f0f8c4dee3f2f" } } ], "extra": [ 1, 147, 197, 55, 3, 15, 4, 33, 48, 198, 202, 153, 142, 50, 3, 91, 80, 3, 226, 51, 181, 251, 90, 169, 224, 183, 190, 104, 114, 169, 178, 110, 131, 2, 17, 0, 0, 0, 5, 74, 15, 80, 19, 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