Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ce3f4a69f37ef78b1d23a7c137ddeb9302a3cd9cb5acaccce12aac94d00d4482

Tx prefix hash: bb0bf64451dd01148379a644e75a7d330492ce91e6c887ee76f21e4d6c9e8d8a
Tx public key: bf636867ea997d21697a026a04e84d731b053e0c3e6a1358c321937d639c6e15
Timestamp: 1735706902 Timestamp [UCT]: 2025-01-01 04:48:22 Age [y:d:h:m:s]: 00:106:11:20:51
Block: 1187641 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 75886 RingCT/type: yes/0
Extra: 01bf636867ea997d21697a026a04e84d731b053e0c3e6a1358c321937d639c6e15021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 10330a8be7f0d3f7c83ecdf64ab9b0b91eaf36716f4444106507d79763b8695a 0.600000000000 1674134 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": 1187651, "vin": [ { "gen": { "height": 1187641 } } ], "vout": [ { "amount": 600000000, "target": { "key": "10330a8be7f0d3f7c83ecdf64ab9b0b91eaf36716f4444106507d79763b8695a" } } ], "extra": [ 1, 191, 99, 104, 103, 234, 153, 125, 33, 105, 122, 2, 106, 4, 232, 77, 115, 27, 5, 62, 12, 62, 106, 19, 88, 195, 33, 147, 125, 99, 156, 110, 21, 2, 17, 0, 0, 0, 3, 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