Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d41928f6fc89ed658e037473dc7e07d20ac37d6687f6b5caa5f5b8f7e74aada3

Tx prefix hash: 095ba94a201f6eead6130229e772ba583a33a5c6bc7712895e141f93e48f6bf9
Tx public key: 790498c6233a4741480f237b69e34e158fd9cda0b5a9d685e1161948cc8eceb1
Timestamp: 1707584193 Timestamp [UCT]: 2024-02-10 16:56:33 Age [y:d:h:m:s]: 00:316:03:41:03
Block: 954616 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 226382 RingCT/type: yes/0
Extra: 01790498c6233a4741480f237b69e34e158fd9cda0b5a9d685e1161948cc8eceb102110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9f9aea7e2ed1dd2399cb2f14a4fa54bf8493e5d162cff5e973a5ed6f42cf850f 0.600000000000 1413896 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": 954626, "vin": [ { "gen": { "height": 954616 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9f9aea7e2ed1dd2399cb2f14a4fa54bf8493e5d162cff5e973a5ed6f42cf850f" } } ], "extra": [ 1, 121, 4, 152, 198, 35, 58, 71, 65, 72, 15, 35, 123, 105, 227, 78, 21, 143, 217, 205, 160, 181, 169, 214, 133, 225, 22, 25, 72, 204, 142, 206, 177, 2, 17, 0, 0, 0, 2, 89, 218, 211, 245, 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