Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5cbc2d525ce65f080f23aec1c9b4b8b0102c719ce2248d3fcc029c48fbebf8e5

Tx prefix hash: 0515edbbbf9e9ef5ae4ad58766df4a07c27b202c720f40f46605e7bd57d00206
Tx public key: 56e51290f635221b54ea574555ce8ce2b07fe845ab4b25431a0c68d2e026a6d4
Timestamp: 1714330920 Timestamp [UCT]: 2024-04-28 19:02:00 Age [y:d:h:m:s]: 00:209:20:21:19
Block: 1010549 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 150231 RingCT/type: yes/0
Extra: 0156e51290f635221b54ea574555ce8ce2b07fe845ab4b25431a0c68d2e026a6d402110000000959dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c176daaf2dad356cbe8ef7da10be13693b8db89d5dbde68b059b8d94ecb04481 0.600000000000 1472539 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": 1010559, "vin": [ { "gen": { "height": 1010549 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c176daaf2dad356cbe8ef7da10be13693b8db89d5dbde68b059b8d94ecb04481" } } ], "extra": [ 1, 86, 229, 18, 144, 246, 53, 34, 27, 84, 234, 87, 69, 85, 206, 140, 226, 176, 127, 232, 69, 171, 75, 37, 67, 26, 12, 104, 210, 224, 38, 166, 212, 2, 17, 0, 0, 0, 9, 89, 218, 211, 245, 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