Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a8576ccbd5df10661b352db3f88caa86e7d9b3e746c83954079a433d760f29e4

Tx prefix hash: 2752427c4d61a4e86cfe118c48983495291683a417fad85553feb2923fee34e7
Tx public key: ee918439aa0f921aaac5a30a07bf3bab57dc01bbdae0a1a89b60984bb51c2a0c
Timestamp: 1720602787 Timestamp [UCT]: 2024-07-10 09:13:07 Age [y:d:h:m:s]: 01:119:07:39:51
Block: 1062563 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 343769 RingCT/type: yes/0
Extra: 01ee918439aa0f921aaac5a30a07bf3bab57dc01bbdae0a1a89b60984bb51c2a0c021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b822f8db4e7790c0907287f0bcf8d03eaa83c0259480ba49e03615d84857c510 0.600000000000 1533068 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": 1062573, "vin": [ { "gen": { "height": 1062563 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b822f8db4e7790c0907287f0bcf8d03eaa83c0259480ba49e03615d84857c510" } } ], "extra": [ 1, 238, 145, 132, 57, 170, 15, 146, 26, 170, 197, 163, 10, 7, 191, 59, 171, 87, 220, 1, 187, 218, 224, 161, 168, 155, 96, 152, 75, 181, 28, 42, 12, 2, 17, 0, 0, 0, 2, 233, 20, 221, 21, 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