Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8f56d49a8a841ddb5047d275d4241b679083a655dcc3f49a66c456de0def4b5e

Tx prefix hash: 31e5d11a4c4ea9f32a0b17f4b07cf60f49b6fa4333fbca70ff490e21dad414d6
Tx public key: 63b030b74260130cf2d31dfa83c96449d5ff81c6af89aa98c4360c8916deda8d
Timestamp: 1703100277 Timestamp [UCT]: 2023-12-20 19:24:37 Age [y:d:h:m:s]: 01:329:15:21:45
Block: 917465 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 494428 RingCT/type: yes/0
Extra: 0163b030b74260130cf2d31dfa83c96449d5ff81c6af89aa98c4360c8916deda8d02110000000179bda3be000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6c5835149a0ad8cfabdd68ae7e671893112988e95e910d6c1cf4fe04c8de3b4b 0.600000000000 1375047 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": 917475, "vin": [ { "gen": { "height": 917465 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6c5835149a0ad8cfabdd68ae7e671893112988e95e910d6c1cf4fe04c8de3b4b" } } ], "extra": [ 1, 99, 176, 48, 183, 66, 96, 19, 12, 242, 211, 29, 250, 131, 201, 100, 73, 213, 255, 129, 198, 175, 137, 170, 152, 196, 54, 12, 137, 22, 222, 218, 141, 2, 17, 0, 0, 0, 1, 121, 189, 163, 190, 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