Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4b0b532e8baeada4ef4746ed99095bde5073361b23c916fa7f824aa482641e0b

Tx prefix hash: f410782cf106232b49f877598ea8b4b0f2e80d62c9b85eb02f4b3a2c896d5901
Tx public key: 297315503bdf1f7f866f97db198b7fcbe805b3a6df2eebed756787c9abba5794
Timestamp: 1728856435 Timestamp [UCT]: 2024-10-13 21:53:55 Age [y:d:h:m:s]: 00:191:17:39:43
Block: 1130978 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 136828 RingCT/type: yes/0
Extra: 01297315503bdf1f7f866f97db198b7fcbe805b3a6df2eebed756787c9abba5794021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 89ac8ff09c2a7fb42152cb2a05e861edc3fd7d5470ae72ca66b3541f68a614e4 0.600000000000 1613859 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": 1130988, "vin": [ { "gen": { "height": 1130978 } } ], "vout": [ { "amount": 600000000, "target": { "key": "89ac8ff09c2a7fb42152cb2a05e861edc3fd7d5470ae72ca66b3541f68a614e4" } } ], "extra": [ 1, 41, 115, 21, 80, 59, 223, 31, 127, 134, 111, 151, 219, 25, 139, 127, 203, 232, 5, 179, 166, 223, 46, 235, 237, 117, 103, 135, 201, 171, 186, 87, 148, 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