Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b4d51f61034ccfc3c6b2304457a719be71d3210c57c00806533b1ad5da510c74

Tx prefix hash: 4c6aa703c9e5817d884fd2a81353508f368f3523e075d53b9ccc282b37c71720
Tx public key: 02faba6ef84302926d1a14b5a89a0636423e88bb0f96ad0c69d19a99a06d1dc4
Timestamp: 1764425491 Timestamp [UCT]: 2025-11-29 14:11:31 Age [y:d:h:m:s]: 00:000:13:36:16
Block: 1422741 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 403 RingCT/type: yes/0
Extra: 0102faba6ef84302926d1a14b5a89a0636423e88bb0f96ad0c69d19a99a06d1dc4021100000003da554848000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6167b01de6b49f96234af540010d071c3e9c10148ef553fe2635454cddf554e0 0.600000000000 1911314 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": 1422751, "vin": [ { "gen": { "height": 1422741 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6167b01de6b49f96234af540010d071c3e9c10148ef553fe2635454cddf554e0" } } ], "extra": [ 1, 2, 250, 186, 110, 248, 67, 2, 146, 109, 26, 20, 181, 168, 154, 6, 54, 66, 62, 136, 187, 15, 150, 173, 12, 105, 209, 154, 153, 160, 109, 29, 196, 2, 17, 0, 0, 0, 3, 218, 85, 72, 72, 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