Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a0769180e34a8e489d5952adbc29d596d6786ee5c270a97f28fcd5507dae143b

Tx prefix hash: 53135dbaaee0631f557f0bcda07fae489c4ae60d5c56c331594218554e57427e
Tx public key: 0f0c6bb498596b710e8d3ea3e815f4661406c6dcf3e2bd2ec40a6373f5d0e61f
Timestamp: 1735627711 Timestamp [UCT]: 2024-12-31 06:48:31 Age [y:d:h:m:s]: 00:169:17:46:57
Block: 1186987 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 121021 RingCT/type: yes/0
Extra: 010f0c6bb498596b710e8d3ea3e815f4661406c6dcf3e2bd2ec40a6373f5d0e61f021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0fb8b1ce943e6701aec8782c1d6f5bdad1d43a0a0beaa2f6c01f3ccc2405fda6 0.600000000000 1673474 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": 1186997, "vin": [ { "gen": { "height": 1186987 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0fb8b1ce943e6701aec8782c1d6f5bdad1d43a0a0beaa2f6c01f3ccc2405fda6" } } ], "extra": [ 1, 15, 12, 107, 180, 152, 89, 107, 113, 14, 141, 62, 163, 232, 21, 244, 102, 20, 6, 198, 220, 243, 226, 189, 46, 196, 10, 99, 115, 245, 208, 230, 31, 2, 17, 0, 0, 0, 3, 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