Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3617fd8e8eee5d2e6f15cb10c7316ee2541dc87b60745ed6425d082f7d579bde

Tx prefix hash: 874129544ee5bd4ab0a332c36d3974ff53c229724c76d2acc5d4cc0ae3605c2c
Tx public key: a5092c0baa48e91f997412d0c725d4e406145ee5036c84e91a0063ef133a7cb8
Timestamp: 1731200842 Timestamp [UCT]: 2024-11-10 01:07:22 Age [y:d:h:m:s]: 00:147:06:26:31
Block: 1150334 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 105071 RingCT/type: yes/0
Extra: 01a5092c0baa48e91f997412d0c725d4e406145ee5036c84e91a0063ef133a7cb8021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ac5eb9536e5e2d8db1590951bd20763f825fd6489b244e1dd4eeea7afcb2ea12 0.600000000000 1635615 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": 1150344, "vin": [ { "gen": { "height": 1150334 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ac5eb9536e5e2d8db1590951bd20763f825fd6489b244e1dd4eeea7afcb2ea12" } } ], "extra": [ 1, 165, 9, 44, 11, 170, 72, 233, 31, 153, 116, 18, 208, 199, 37, 212, 228, 6, 20, 94, 229, 3, 108, 132, 233, 26, 0, 99, 239, 19, 58, 124, 184, 2, 17, 0, 0, 0, 1, 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