Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1cb5f41166a996b31b8bc7cf11e8332235cdb03c58e6e49e861858cbb8742edf

Tx prefix hash: 2d0ce059f149d8d5e64505ae43bd1d9eb1467ac7b75f96ef5c183973303173c7
Tx public key: f504862cc4dcafe9e1cced034fa123c109b02238ec42c35df77799fb40b4e070
Timestamp: 1699686570 Timestamp [UCT]: 2023-11-11 07:09:30 Age [y:d:h:m:s]: 01:135:07:39:56
Block: 889150 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 357885 RingCT/type: yes/0
Extra: 01f504862cc4dcafe9e1cced034fa123c109b02238ec42c35df77799fb40b4e070021100000005faf35c9c000000000000000000

1 output(s) for total of 0.694827415000 dcy

stealth address amount amount idx
00: a02047def265cd59a62bc3271c25b07e2e24418b89f6e597fcc4b44779b7fb83 0.694827415000 1345127 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": 889160, "vin": [ { "gen": { "height": 889150 } } ], "vout": [ { "amount": 694827415, "target": { "key": "a02047def265cd59a62bc3271c25b07e2e24418b89f6e597fcc4b44779b7fb83" } } ], "extra": [ 1, 245, 4, 134, 44, 196, 220, 175, 233, 225, 204, 237, 3, 79, 161, 35, 193, 9, 176, 34, 56, 236, 66, 195, 93, 247, 119, 153, 251, 64, 180, 224, 112, 2, 17, 0, 0, 0, 5, 250, 243, 92, 156, 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