Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bb04693aaee532c7a199edecadc1c7d68d37352ea4a4eb9b595afb276c9592d2

Tx prefix hash: c059eb64191619936bc5098073bb18ed96ad6d568564d9ccb533d49529f6078e
Tx public key: c094f8f0d876bc0d82b2a55443d048897f98583e05b1d8535d33adc51145bfe2
Timestamp: 1722094286 Timestamp [UCT]: 2024-07-27 15:31:26 Age [y:d:h:m:s]: 00:263:14:09:56
Block: 1074917 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 188300 RingCT/type: yes/0
Extra: 01c094f8f0d876bc0d82b2a55443d048897f98583e05b1d8535d33adc51145bfe2021100000016e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 33bdda840a162757af6f13afd85e85f9fcb756b714f503437dc06416176aaf28 0.600000000000 1547436 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": 1074927, "vin": [ { "gen": { "height": 1074917 } } ], "vout": [ { "amount": 600000000, "target": { "key": "33bdda840a162757af6f13afd85e85f9fcb756b714f503437dc06416176aaf28" } } ], "extra": [ 1, 192, 148, 248, 240, 216, 118, 188, 13, 130, 178, 165, 84, 67, 208, 72, 137, 127, 152, 88, 62, 5, 177, 216, 83, 93, 51, 173, 197, 17, 69, 191, 226, 2, 17, 0, 0, 0, 22, 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