Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 68231502610f1342da6909f7cc21751b8e11c8fca56b51e5787e62f09b595bc9

Tx prefix hash: d0b3654386328e1d5dc6fe90941d693862ee77033b21ad9704b6ba6a00d2ccbf
Tx public key: faa47cff98b0ed20112dc605468a686da927a7f0f517e2f1da05731bd5abdf87
Timestamp: 1725773614 Timestamp [UCT]: 2024-09-08 05:33:34 Age [y:d:h:m:s]: 00:044:22:52:07
Block: 1105423 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 32168 RingCT/type: yes/0
Extra: 01faa47cff98b0ed20112dc605468a686da927a7f0f517e2f1da05731bd5abdf87021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2dac856539577f7e7e64e0bed9d2bf7397b5a6a580251e405ceb8f81c5f1e6a4 0.600000000000 1582766 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": 1105433, "vin": [ { "gen": { "height": 1105423 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2dac856539577f7e7e64e0bed9d2bf7397b5a6a580251e405ceb8f81c5f1e6a4" } } ], "extra": [ 1, 250, 164, 124, 255, 152, 176, 237, 32, 17, 45, 198, 5, 70, 138, 104, 109, 169, 39, 167, 240, 245, 23, 226, 241, 218, 5, 115, 27, 213, 171, 223, 135, 2, 17, 0, 0, 0, 2, 233, 20, 221, 21, 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