Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d74bc279b56dcff919cd9fdb71a536c356ece2a2ce46db9e0e1fe0c0e1b1e74b

Tx prefix hash: 7697d4d7b450f1d26b0d3671034c04bc4cbcb47d9343f3ae42afe44e0d53aab3
Tx public key: bff876ea6e1dd1244d98c2bdd6087eef77d5948674a320e26af482641ee6281d
Timestamp: 1702395397 Timestamp [UCT]: 2023-12-12 15:36:37 Age [y:d:h:m:s]: 01:331:11:34:24
Block: 911623 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 495750 RingCT/type: yes/0
Extra: 01bff876ea6e1dd1244d98c2bdd6087eef77d5948674a320e26af482641ee6281d02110000000575e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8ec2cb88b31a7395897fdd0ec1a4f2790bacd33db72e79b9348f0218a051d484 0.600000000000 1368837 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": 911633, "vin": [ { "gen": { "height": 911623 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8ec2cb88b31a7395897fdd0ec1a4f2790bacd33db72e79b9348f0218a051d484" } } ], "extra": [ 1, 191, 248, 118, 234, 110, 29, 209, 36, 77, 152, 194, 189, 214, 8, 126, 239, 119, 213, 148, 134, 116, 163, 32, 226, 106, 244, 130, 100, 30, 230, 40, 29, 2, 17, 0, 0, 0, 5, 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