Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2d635d15651e8acf44e1869e749753212f097219e6c57b876816e3d74dce3ed2

Tx prefix hash: 6be35e14353dd6442426537465288462888f5608a0de77c59cdab20c8df9d2a2
Tx public key: a900bbcc4422e5c4697c324362d5edac4f922c797df071a0fa4969a77a06b6eb
Timestamp: 1736144021 Timestamp [UCT]: 2025-01-06 06:13:41 Age [y:d:h:m:s]: 00:100:01:26:48
Block: 1191279 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 71278 RingCT/type: yes/0
Extra: 01a900bbcc4422e5c4697c324362d5edac4f922c797df071a0fa4969a77a06b6eb0211000000071f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cc2c1f8ffce5d6f1f4b233ea596aa3970623857bb03e4c35925f48c1a4f8fab0 0.600000000000 1677804 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": 1191289, "vin": [ { "gen": { "height": 1191279 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cc2c1f8ffce5d6f1f4b233ea596aa3970623857bb03e4c35925f48c1a4f8fab0" } } ], "extra": [ 1, 169, 0, 187, 204, 68, 34, 229, 196, 105, 124, 50, 67, 98, 213, 237, 172, 79, 146, 44, 121, 125, 240, 113, 160, 250, 73, 105, 167, 122, 6, 182, 235, 2, 17, 0, 0, 0, 7, 31, 10, 83, 235, 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