Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d1ffc681a820d684ed4e1e521a3fb6ee4b8b1dd872e22c0767ae45782b463518

Tx prefix hash: 316944ac8a7363ed23e1ddeb5600b19c9a26288871834cbff8468b242951d21a
Tx public key: 1e92ed7cd145e102ad021ebd82a603e84e339514c337d1113c1cc3a9922f299e
Timestamp: 1749488039 Timestamp [UCT]: 2025-06-09 16:53:59 Age [y:d:h:m:s]: 00:161:04:31:13
Block: 1301476 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 112883 RingCT/type: yes/0
Extra: 011e92ed7cd145e102ad021ebd82a603e84e339514c337d1113c1cc3a9922f299e02110000000125a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b7955d9af1000d78babf9388a406d8b993c0ed970237d9f627b48f2827fd0649 0.600000000000 1789035 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": 1301486, "vin": [ { "gen": { "height": 1301476 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b7955d9af1000d78babf9388a406d8b993c0ed970237d9f627b48f2827fd0649" } } ], "extra": [ 1, 30, 146, 237, 124, 209, 69, 225, 2, 173, 2, 30, 189, 130, 166, 3, 232, 78, 51, 149, 20, 195, 55, 209, 17, 60, 28, 195, 169, 146, 47, 41, 158, 2, 17, 0, 0, 0, 1, 37, 163, 90, 15, 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