Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b4fbc0fcb7f0b07b220c21df8c4affd5e3b4d08acb76168221b85a2e8434c825

Tx prefix hash: 33d900d46c059306719d8094d4cdce38fc1884ea418ba1789d6617fc9837c658
Tx public key: bfd0c6357b3833b88fc55929956883a32ab75802a8ff527e930b06908b0e1f39
Timestamp: 1746082063 Timestamp [UCT]: 2025-05-01 06:47:43 Age [y:d:h:m:s]: 00:235:15:47:42
Block: 1273257 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 166188 RingCT/type: yes/0
Extra: 01bfd0c6357b3833b88fc55929956883a32ab75802a8ff527e930b06908b0e1f390211000000089f9fe68c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 080cbfdeaf744820bc07acd736efb40cbc1aef781964593e8e5c053cc0f3234e 0.600000000000 1760538 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": 1273267, "vin": [ { "gen": { "height": 1273257 } } ], "vout": [ { "amount": 600000000, "target": { "key": "080cbfdeaf744820bc07acd736efb40cbc1aef781964593e8e5c053cc0f3234e" } } ], "extra": [ 1, 191, 208, 198, 53, 123, 56, 51, 184, 143, 197, 89, 41, 149, 104, 131, 163, 42, 183, 88, 2, 168, 255, 82, 126, 147, 11, 6, 144, 139, 14, 31, 57, 2, 17, 0, 0, 0, 8, 159, 159, 230, 140, 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