Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d35b169eee40ffe3bdfe1b5d03f5cfca353773c02fd23d0383fe516b5cc3e1b8

Tx prefix hash: 399dde49f313855b56bc17048651c751b33823d5c3de70935185dc1a8ec9def0
Tx public key: 0b48521b23d74ca973808e4bf1a603c1770261ea9099d816d24dc04094e253c1
Timestamp: 1735562697 Timestamp [UCT]: 2024-12-30 12:44:57 Age [y:d:h:m:s]: 00:122:01:59:19
Block: 1186448 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 87046 RingCT/type: yes/0
Extra: 010b48521b23d74ca973808e4bf1a603c1770261ea9099d816d24dc04094e253c102110000000a007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 87ed7bfd56ea7f05253c0a70e60280dbb9754b332945376b6d006b9968f51f5c 0.600000000000 1672929 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": 1186458, "vin": [ { "gen": { "height": 1186448 } } ], "vout": [ { "amount": 600000000, "target": { "key": "87ed7bfd56ea7f05253c0a70e60280dbb9754b332945376b6d006b9968f51f5c" } } ], "extra": [ 1, 11, 72, 82, 27, 35, 215, 76, 169, 115, 128, 142, 75, 241, 166, 3, 193, 119, 2, 97, 234, 144, 153, 216, 22, 210, 77, 192, 64, 148, 226, 83, 193, 2, 17, 0, 0, 0, 10, 0, 127, 151, 138, 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