Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1919806935541572f1b1f29f3beda7787fd9c7813ee431517eff9bc7f45936a8

Tx prefix hash: 70281404cbd937ec2f88f1e828c4f389adca51e1d601a4e703d745973d7b7cc3
Tx public key: 9200eaf447f8738b66defec1ee3a3cd349fb09f2a3d25297d19907aa3b3d70d7
Timestamp: 1714341067 Timestamp [UCT]: 2024-04-28 21:51:07 Age [y:d:h:m:s]: 01:030:09:19:15
Block: 1010634 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 282697 RingCT/type: yes/0
Extra: 019200eaf447f8738b66defec1ee3a3cd349fb09f2a3d25297d19907aa3b3d70d702110000000652d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e97c7b29f980033a2ef5d440e15f7f4d1aea7fafd41eb2abd840eb68516b7b30 0.600000000000 1472644 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": 1010644, "vin": [ { "gen": { "height": 1010634 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e97c7b29f980033a2ef5d440e15f7f4d1aea7fafd41eb2abd840eb68516b7b30" } } ], "extra": [ 1, 146, 0, 234, 244, 71, 248, 115, 139, 102, 222, 254, 193, 238, 58, 60, 211, 73, 251, 9, 242, 163, 210, 82, 151, 209, 153, 7, 170, 59, 61, 112, 215, 2, 17, 0, 0, 0, 6, 82, 212, 126, 148, 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