Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5593f6fe86de4f1e589726a59a7f32231f650a114917cfa86426e68172d77baf

Tx prefix hash: 5e7fef42afe6f83f4231ba5f5ee6b6f686ac0915415b1b7fdc2183fd9fd332f3
Tx public key: f61374c58e58eee8d8b49c161e9b899e8f6e9bd80ea0c2ba714ed279c69db34e
Timestamp: 1634669091 Timestamp [UCT]: 2021-10-19 18:44:51 Age [y:d:h:m:s]: 03:037:16:43:05
Block: 356337 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 805031 RingCT/type: yes/0
Extra: 01f61374c58e58eee8d8b49c161e9b899e8f6e9bd80ea0c2ba714ed279c69db34e0211000000128d0de867000000000000000000

1 output(s) for total of 40.486292720000 dcy

stealth address amount amount idx
00: a6eb8e75c0b3ee1e1380ded92719f597f097b71fd596d851c636122625b2902b 40.486292720000 727093 of 0

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": 356347, "vin": [ { "gen": { "height": 356337 } } ], "vout": [ { "amount": 40486292720, "target": { "key": "a6eb8e75c0b3ee1e1380ded92719f597f097b71fd596d851c636122625b2902b" } } ], "extra": [ 1, 246, 19, 116, 197, 142, 88, 238, 232, 216, 180, 156, 22, 30, 155, 137, 158, 143, 110, 155, 216, 14, 160, 194, 186, 113, 78, 210, 121, 198, 157, 179, 78, 2, 17, 0, 0, 0, 18, 141, 13, 232, 103, 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