Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a0d7de07f9bfbaad80eed66cf11452a235c5c1f2649e8a47c7ae2e2943b241b4

Tx prefix hash: 7fa4437a818cb7c178ccc6fc56c3ba048a0699aedebf19d7b285dc4266386bc9
Tx public key: 267eb4f5679b27ad0a52f2db714e9e30da4f26c1ec229f0f1520dd804eb6ce54
Timestamp: 1737875860 Timestamp [UCT]: 2025-01-26 07:17:40 Age [y:d:h:m:s]: 00:146:09:58:21
Block: 1205554 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 104337 RingCT/type: yes/0
Extra: 01267eb4f5679b27ad0a52f2db714e9e30da4f26c1ec229f0f1520dd804eb6ce54021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 69683813dc8ca5224622d6cad6f66f3a800a6f586c76dd79db6e62cdf159b9e9 0.600000000000 1692251 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": 1205564, "vin": [ { "gen": { "height": 1205554 } } ], "vout": [ { "amount": 600000000, "target": { "key": "69683813dc8ca5224622d6cad6f66f3a800a6f586c76dd79db6e62cdf159b9e9" } } ], "extra": [ 1, 38, 126, 180, 245, 103, 155, 39, 173, 10, 82, 242, 219, 113, 78, 158, 48, 218, 79, 38, 193, 236, 34, 159, 15, 21, 32, 221, 128, 78, 182, 206, 84, 2, 17, 0, 0, 0, 4, 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