Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 49c5db5426c89f7b720da6757335a68f628f9a5019e30b00406bf68a23fb0bfe

Tx prefix hash: 4d7fa3a91e36fe7b1df74a4ec756e765cbf032f2f9650c30a270c919df9e2915
Tx public key: f8b53c3a4db055e3cf697895c8f8aaea7f2c6ae70d2bd34e081674c89c6039ac
Timestamp: 1703744138 Timestamp [UCT]: 2023-12-28 06:15:38 Age [y:d:h:m:s]: 01:317:01:26:06
Block: 922789 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 485429 RingCT/type: yes/0
Extra: 01f8b53c3a4db055e3cf697895c8f8aaea7f2c6ae70d2bd34e081674c89c6039ac02110000000659dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d915954713288a916231dd2cf5b5b9a9968d73af7cb1b080d26f2df699678a50 0.600000000000 1380493 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": 922799, "vin": [ { "gen": { "height": 922789 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d915954713288a916231dd2cf5b5b9a9968d73af7cb1b080d26f2df699678a50" } } ], "extra": [ 1, 248, 181, 60, 58, 77, 176, 85, 227, 207, 105, 120, 149, 200, 248, 170, 234, 127, 44, 106, 231, 13, 43, 211, 78, 8, 22, 116, 200, 156, 96, 57, 172, 2, 17, 0, 0, 0, 6, 89, 218, 211, 245, 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