Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c6aa97b457fc9fd789f518157c03472bf14a71b40c3091ae9b6025d1818a714a

Tx prefix hash: f1b5477d55ea94ae4ceaa89a18a2e0637556858d773fb0d3268d0118da9a8c23
Tx public key: 3025826a2deae87f82b3003c2b1c4c104345362efdef7bd6686dde6a35cb2467
Timestamp: 1704924665 Timestamp [UCT]: 2024-01-10 22:11:05 Age [y:d:h:m:s]: 01:156:20:38:12
Block: 932560 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 373161 RingCT/type: yes/0
Extra: 013025826a2deae87f82b3003c2b1c4c104345362efdef7bd6686dde6a35cb2467021100000005679a8a81000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b754620008bfd36306b5da7ee63a3c89219475d548cdd8543503a09fbe2ce21b 0.600000000000 1390496 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": 932570, "vin": [ { "gen": { "height": 932560 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b754620008bfd36306b5da7ee63a3c89219475d548cdd8543503a09fbe2ce21b" } } ], "extra": [ 1, 48, 37, 130, 106, 45, 234, 232, 127, 130, 179, 0, 60, 43, 28, 76, 16, 67, 69, 54, 46, 253, 239, 123, 214, 104, 109, 222, 106, 53, 203, 36, 103, 2, 17, 0, 0, 0, 5, 103, 154, 138, 129, 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