Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cdd8ae21dddeabd4a2fb2c1e2c781727ad96a9afaa1397eca4230720ab621775

Tx prefix hash: c38a6608fe85ddcb86f7d476ad51de4ae30ae7b2a667c1bc5e29bbe8fe910f42
Tx public key: f3a4b075ec2ce6dbcc512e7aa99f44a886cb782910865aaf26ae1a69121fa3e5
Timestamp: 1716188807 Timestamp [UCT]: 2024-05-20 07:06:47 Age [y:d:h:m:s]: 00:350:16:07:05
Block: 1025964 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 250647 RingCT/type: yes/0
Extra: 01f3a4b075ec2ce6dbcc512e7aa99f44a886cb782910865aaf26ae1a69121fa3e5021100000002e08532b6000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5ccc652bf554760677376d6d053970eade3081da587757e8f2e115399b1cb320 0.600000000000 1492785 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": 1025974, "vin": [ { "gen": { "height": 1025964 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5ccc652bf554760677376d6d053970eade3081da587757e8f2e115399b1cb320" } } ], "extra": [ 1, 243, 164, 176, 117, 236, 44, 230, 219, 204, 81, 46, 122, 169, 159, 68, 168, 134, 203, 120, 41, 16, 134, 90, 175, 38, 174, 26, 105, 18, 31, 163, 229, 2, 17, 0, 0, 0, 2, 224, 133, 50, 182, 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