Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6624973acd4a34033a0978ec1eec50d4bc224bbde6d97367559536f02ee4cb5b

Tx prefix hash: ef553c7f9a19a0ea5e1f0579c5fac17db7a2e0fb977b2089353eaa325fb88d01
Tx public key: f87d9bb40cc4f08be1ec69e90a745ae8179ce5e59c57a66281c4a0787d6deb05
Timestamp: 1693361996 Timestamp [UCT]: 2023-08-30 02:19:56 Age [y:d:h:m:s]: 01:239:00:57:38
Block: 836894 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 431980 RingCT/type: yes/0
Extra: 01f87d9bb40cc4f08be1ec69e90a745ae8179ce5e59c57a66281c4a0787d6deb050211000000036cce3ea6000000000000000000

1 output(s) for total of 1.035196614000 dcy

stealth address amount amount idx
00: 90870ba845fe96d2a43bc3db1ecd5662d49c88ae8eee1c1554001c2a973e2a82 1.035196614000 1289500 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": 836904, "vin": [ { "gen": { "height": 836894 } } ], "vout": [ { "amount": 1035196614, "target": { "key": "90870ba845fe96d2a43bc3db1ecd5662d49c88ae8eee1c1554001c2a973e2a82" } } ], "extra": [ 1, 248, 125, 155, 180, 12, 196, 240, 139, 225, 236, 105, 233, 10, 116, 90, 232, 23, 156, 229, 229, 156, 87, 166, 98, 129, 196, 160, 120, 125, 109, 235, 5, 2, 17, 0, 0, 0, 3, 108, 206, 62, 166, 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