Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b16c48aa5c848619d7e85367656f9bdde6784174fba13c9557f1b5743d6e9a90

Tx prefix hash: 460835e1ee004ee94f6d8616e011ebf2401e00330c3d0ae8da81bec435298c5e
Tx public key: 4fee3092564aea2b88748c875e9324dbd82ba0ddb89923a95a37d88f4e45e97f
Timestamp: 1728636890 Timestamp [UCT]: 2024-10-11 08:54:50 Age [y:d:h:m:s]: 00:168:20:47:45
Block: 1129160 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 120466 RingCT/type: yes/0
Extra: 014fee3092564aea2b88748c875e9324dbd82ba0ddb89923a95a37d88f4e45e97f021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8096fc5bc6b25a5cee782a820b5a4ae7cd9122057aece2d0f8c9fe08f35fcbf0 0.600000000000 1611985 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": 1129170, "vin": [ { "gen": { "height": 1129160 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8096fc5bc6b25a5cee782a820b5a4ae7cd9122057aece2d0f8c9fe08f35fcbf0" } } ], "extra": [ 1, 79, 238, 48, 146, 86, 74, 234, 43, 136, 116, 140, 135, 94, 147, 36, 219, 216, 43, 160, 221, 184, 153, 35, 169, 90, 55, 216, 143, 78, 69, 233, 127, 2, 17, 0, 0, 0, 3, 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