Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4ecbd19253be49956c0e48893c2a6e85e59a99c75591de867271ce7a44fc1921

Tx prefix hash: 5a52452dce8c1579d442f9099f27da9a96a13991006c09723fa74e9eae66760c
Tx public key: 20190769f5f7a0a8a7db2de8dbf3ea62a3dd33734c039019817932d2dc3111bd
Timestamp: 1703033540 Timestamp [UCT]: 2023-12-20 00:52:20 Age [y:d:h:m:s]: 01:178:10:36:35
Block: 916898 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 388605 RingCT/type: yes/0
Extra: 0120190769f5f7a0a8a7db2de8dbf3ea62a3dd33734c039019817932d2dc3111bd02110000000475e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 69918397842fde9e254982c248a7eda5f6a3d3ebd2a5db8d7845a557285fe93d 0.600000000000 1374460 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": 916908, "vin": [ { "gen": { "height": 916898 } } ], "vout": [ { "amount": 600000000, "target": { "key": "69918397842fde9e254982c248a7eda5f6a3d3ebd2a5db8d7845a557285fe93d" } } ], "extra": [ 1, 32, 25, 7, 105, 245, 247, 160, 168, 167, 219, 45, 232, 219, 243, 234, 98, 163, 221, 51, 115, 76, 3, 144, 25, 129, 121, 50, 210, 220, 49, 17, 189, 2, 17, 0, 0, 0, 4, 117, 227, 240, 233, 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