Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bdc362bb5c4d3851430dbfb8318c1559360304b642d78c6c618fae1887abcd7f

Tx prefix hash: 628fdb3a811eef39468321792e99daf791368cb34af386b13dbb4c0616152f56
Tx public key: df9e5fc68b405c2da94893a1e700817f64fe738a4406ea39aa3acf3842d445cc
Timestamp: 1739057374 Timestamp [UCT]: 2025-02-08 23:29:34 Age [y:d:h:m:s]: 00:357:12:50:22
Block: 1215115 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 253202 RingCT/type: yes/0
Extra: 01df9e5fc68b405c2da94893a1e700817f64fe738a4406ea39aa3acf3842d445cc021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: be6b8515fde8e72a34bc08a91d4aa8558da663d514e257cf2cfcbc271c33d3e2 0.600000000000 1701912 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": 1215125, "vin": [ { "gen": { "height": 1215115 } } ], "vout": [ { "amount": 600000000, "target": { "key": "be6b8515fde8e72a34bc08a91d4aa8558da663d514e257cf2cfcbc271c33d3e2" } } ], "extra": [ 1, 223, 158, 95, 198, 139, 64, 92, 45, 169, 72, 147, 161, 231, 0, 129, 127, 100, 254, 115, 138, 68, 6, 234, 57, 170, 58, 207, 56, 66, 212, 69, 204, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 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