Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8e0215d32397d9428be1e4cb84f9ebf8303fb23ef3c60643941320a8f9922df7

Tx prefix hash: e7b0a6f6e9d5d786577bcd41ebf4d06bfff2ab1afa1697e5698704fd4d60c582
Tx public key: fc2d5590e4a44ede611505f79fbc0c39c04777c6394b75ab97b186cb80f0a849
Timestamp: 1736998291 Timestamp [UCT]: 2025-01-16 03:31:31 Age [y:d:h:m:s]: 00:153:20:46:23
Block: 1198327 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 109670 RingCT/type: yes/0
Extra: 01fc2d5590e4a44ede611505f79fbc0c39c04777c6394b75ab97b186cb80f0a849021100000006007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: dbc7a7758143eea72246b3d9c403c9461b86c5ba75a8f10a814336570f68203c 0.600000000000 1684950 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": 1198337, "vin": [ { "gen": { "height": 1198327 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dbc7a7758143eea72246b3d9c403c9461b86c5ba75a8f10a814336570f68203c" } } ], "extra": [ 1, 252, 45, 85, 144, 228, 164, 78, 222, 97, 21, 5, 247, 159, 188, 12, 57, 192, 71, 119, 198, 57, 75, 117, 171, 151, 177, 134, 203, 128, 240, 168, 73, 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