Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7b6f03efe2f0d40dfdda28ddfcbcafbd31a07134d92f20da1f3b646f1dab3e81

Tx prefix hash: 8f0d56a97a309aba876077708216fe2d4af3466cf2c6abfda8d050aa8bf7aa0d
Tx public key: 557d00bf813527522f3bf4bc020599ca8aded2915d0e37925f4832da84a851d9
Timestamp: 1730142381 Timestamp [UCT]: 2024-10-28 19:06:21 Age [y:d:h:m:s]: 00:165:11:37:34
Block: 1141571 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 118109 RingCT/type: yes/0
Extra: 01557d00bf813527522f3bf4bc020599ca8aded2915d0e37925f4832da84a851d90211000000018368266d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9c1725d988c09c3b7ac2b0a7f3bae692bd8a164b8d4ab4bb90957fb73ee8b7ac 0.600000000000 1625378 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": 1141581, "vin": [ { "gen": { "height": 1141571 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9c1725d988c09c3b7ac2b0a7f3bae692bd8a164b8d4ab4bb90957fb73ee8b7ac" } } ], "extra": [ 1, 85, 125, 0, 191, 129, 53, 39, 82, 47, 59, 244, 188, 2, 5, 153, 202, 138, 222, 210, 145, 93, 14, 55, 146, 95, 72, 50, 218, 132, 168, 81, 217, 2, 17, 0, 0, 0, 1, 131, 104, 38, 109, 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