Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 985e785fb0128121e364278afd618065dbc8bcc98691808cdccfcff5574d13e2

Tx prefix hash: ff1ce3064b7f4ab71b6d3157a988f6e8d266b7304150feb4201bcf4dd2b254e0
Tx public key: 3f4e9a63fa64639c805bd4110f0f533e43635b867b5744ac4e82f67b6d1a3eb5
Timestamp: 1737846457 Timestamp [UCT]: 2025-01-25 23:07:37 Age [y:d:h:m:s]: 00:048:01:30:53
Block: 1205312 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 34171 RingCT/type: yes/0
Extra: 013f4e9a63fa64639c805bd4110f0f533e43635b867b5744ac4e82f67b6d1a3eb5021100000006007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a1f69c54510be1dc644da48b5d17a96b1f9dbfe731e02446fed8aa468d44a235 0.600000000000 1692009 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": 1205322, "vin": [ { "gen": { "height": 1205312 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a1f69c54510be1dc644da48b5d17a96b1f9dbfe731e02446fed8aa468d44a235" } } ], "extra": [ 1, 63, 78, 154, 99, 250, 100, 99, 156, 128, 91, 212, 17, 15, 15, 83, 62, 67, 99, 91, 134, 123, 87, 68, 172, 78, 130, 246, 123, 109, 26, 62, 181, 2, 17, 0, 0, 0, 6, 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