Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 309d1ffe9d959f5c71491025aeea754fc0a346c714e6036322f09f7dcb4a9655

Tx prefix hash: fdaa6d8951a38c4da094416011604d2b436eae5684aec23c28364fd1058eb654
Tx public key: ddc9d66b7c72a69433ac5e47918cc243b3a88e6f1f1a6b06b3cb85a38703d04c
Timestamp: 1746051550 Timestamp [UCT]: 2025-04-30 22:19:10 Age [y:d:h:m:s]: 00:274:06:24:45
Block: 1273007 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 193662 RingCT/type: yes/0
Extra: 01ddc9d66b7c72a69433ac5e47918cc243b3a88e6f1f1a6b06b3cb85a38703d04c0211000000031f90517a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9922a4d7e7e74b236ba62edc4c45546d718aa8ad0ba3d47b33e905d28484c8ab 0.600000000000 1760284 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": 1273017, "vin": [ { "gen": { "height": 1273007 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9922a4d7e7e74b236ba62edc4c45546d718aa8ad0ba3d47b33e905d28484c8ab" } } ], "extra": [ 1, 221, 201, 214, 107, 124, 114, 166, 148, 51, 172, 94, 71, 145, 140, 194, 67, 179, 168, 142, 111, 31, 26, 107, 6, 179, 203, 133, 163, 135, 3, 208, 76, 2, 17, 0, 0, 0, 3, 31, 144, 81, 122, 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