Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4b6c22cf6c371d7c8e356fadf856f44c32ee5fd93b14d856fb11f0774d7d07df

Tx prefix hash: a6d92a6843dc658e05b677119912300569eaf527759bc9bfa70a36758f29f092
Tx public key: 732bb4c76551b07b014c2aa95522bd14583a4627a66fc004c9427ee816cf79a5
Timestamp: 1759360602 Timestamp [UCT]: 2025-10-01 23:16:42 Age [y:d:h:m:s]: 00:057:07:58:40
Block: 1380751 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 41061 RingCT/type: yes/0
Extra: 01732bb4c76551b07b014c2aa95522bd14583a4627a66fc004c9427ee816cf79a5021100000002a5dccd79000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fec3264ebfa2e968a503c7bcd2df59c2f5b8c07adbc114c01aacde8f18d3fb8c 0.600000000000 1868862 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": 1380761, "vin": [ { "gen": { "height": 1380751 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fec3264ebfa2e968a503c7bcd2df59c2f5b8c07adbc114c01aacde8f18d3fb8c" } } ], "extra": [ 1, 115, 43, 180, 199, 101, 81, 176, 123, 1, 76, 42, 169, 85, 34, 189, 20, 88, 58, 70, 39, 166, 111, 192, 4, 201, 66, 126, 232, 22, 207, 121, 165, 2, 17, 0, 0, 0, 2, 165, 220, 205, 121, 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