Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e63168a9dca11dafdfb60bd87d932b483f2017b711f9fac4a19622082d4f6bcf

Tx prefix hash: 1ca7df1677621f6883ba3628a9abfaeeff2e9494ebafb84066127458ef6491b5
Tx public key: ed1f98a46a1faf08628da9514c69d2520c3dc885352b3a7300b5d01f3d600ff5
Timestamp: 1704517536 Timestamp [UCT]: 2024-01-06 05:05:36 Age [y:d:h:m:s]: 01:107:05:30:34
Block: 929171 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 337773 RingCT/type: yes/0
Extra: 01ed1f98a46a1faf08628da9514c69d2520c3dc885352b3a7300b5d01f3d600ff50211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a5d34a711c319d7841ecc41ca25d418df14425e2a75a636faa8de4225e5a48ab 0.600000000000 1387039 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": 929181, "vin": [ { "gen": { "height": 929171 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a5d34a711c319d7841ecc41ca25d418df14425e2a75a636faa8de4225e5a48ab" } } ], "extra": [ 1, 237, 31, 152, 164, 106, 31, 175, 8, 98, 141, 169, 81, 76, 105, 210, 82, 12, 61, 200, 133, 53, 43, 58, 115, 0, 181, 208, 31, 61, 96, 15, 245, 2, 17, 0, 0, 0, 1, 0, 17, 5, 91, 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