Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 674a5fe561bb53f77d27a651173bc5fbb15d93b1c108fbca01fd29ebd7f15332

Tx prefix hash: 837618e69aedc88e25e177af61b548b7b57104a57aabe0b2840c5bdea2a2d653
Tx public key: bcb0e35db6e04af319621fcc1026d3362d1e0e804856b3f567f49a3c5f426273
Timestamp: 1727144121 Timestamp [UCT]: 2024-09-24 02:15:21 Age [y:d:h:m:s]: 00:213:04:34:23
Block: 1116785 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 152198 RingCT/type: yes/0
Extra: 01bcb0e35db6e04af319621fcc1026d3362d1e0e804856b3f567f49a3c5f426273021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f997330c02c6199e0cc9853d24a8a3d285805f42b629e014beaafd591b864659 0.600000000000 1597392 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": 1116795, "vin": [ { "gen": { "height": 1116785 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f997330c02c6199e0cc9853d24a8a3d285805f42b629e014beaafd591b864659" } } ], "extra": [ 1, 188, 176, 227, 93, 182, 224, 74, 243, 25, 98, 31, 204, 16, 38, 211, 54, 45, 30, 14, 128, 72, 86, 179, 245, 103, 244, 154, 60, 95, 66, 98, 115, 2, 17, 0, 0, 0, 4, 233, 20, 221, 21, 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