Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1cc7ad5589568e8cfc5d3a64cc5feb80e2d4eacae709cf41e1d0abd34fa035d3

Tx prefix hash: 34c42b80edaf8f5e58681cdec10344c04ff22b61c36a99da6b26101f946e6775
Tx public key: 3ebdcda81d0fa6fae76d9f76f1e98cde338569292aea802c64bd7f60c756f1ab
Timestamp: 1745396581 Timestamp [UCT]: 2025-04-23 08:23:01 Age [y:d:h:m:s]: 00:244:07:34:39
Block: 1267590 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 172369 RingCT/type: yes/0
Extra: 013ebdcda81d0fa6fae76d9f76f1e98cde338569292aea802c64bd7f60c756f1ab0211000000016c98aa3d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d957e4dea3952010ab71a9804daf4b04a58e8b1684f35e2808495ff024418c21 0.600000000000 1754819 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": 1267600, "vin": [ { "gen": { "height": 1267590 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d957e4dea3952010ab71a9804daf4b04a58e8b1684f35e2808495ff024418c21" } } ], "extra": [ 1, 62, 189, 205, 168, 29, 15, 166, 250, 231, 109, 159, 118, 241, 233, 140, 222, 51, 133, 105, 41, 42, 234, 128, 44, 100, 189, 127, 96, 199, 86, 241, 171, 2, 17, 0, 0, 0, 1, 108, 152, 170, 61, 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