Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7ffcf140a7f8f32946a73b37edc128bdc1a2e3aa9233ab0c9e8339b6588ac949

Tx prefix hash: 6ee8db44d6b6ccf42d38e82ba5abe56344884e1648f970cbd83f3b1e014791ac
Tx public key: d97bdcd9b5f26a8370045ca82afe92731cb4e06674d8dcc45b23b802776e22c6
Timestamp: 1715588104 Timestamp [UCT]: 2024-05-13 08:15:04 Age [y:d:h:m:s]: 00:319:11:16:20
Block: 1021005 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 228323 RingCT/type: yes/0
Extra: 01d97bdcd9b5f26a8370045ca82afe92731cb4e06674d8dcc45b23b802776e22c60211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 91c70ee870af7536901a2911b302f94d5e11345bbdc27ed1e9c447ea029af6b3 0.600000000000 1485164 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": 1021015, "vin": [ { "gen": { "height": 1021005 } } ], "vout": [ { "amount": 600000000, "target": { "key": "91c70ee870af7536901a2911b302f94d5e11345bbdc27ed1e9c447ea029af6b3" } } ], "extra": [ 1, 217, 123, 220, 217, 181, 242, 106, 131, 112, 4, 92, 168, 42, 254, 146, 115, 28, 180, 224, 102, 116, 216, 220, 196, 91, 35, 184, 2, 119, 110, 34, 198, 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