Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 557c1b386c7b2d6da2be8ef8d13cb60ee778ab661f7becff41c4478e675e4838

Tx prefix hash: 49f3b0b9059f550fef241af4bea1a521f2243a2b42d4aa8d075f9fd2635f1a8f
Tx public key: 36bec5a6e6131d482b08956ce6fecd48c9faff11a94d6037b96690fe12fac5d6
Timestamp: 1734069691 Timestamp [UCT]: 2024-12-13 06:01:31 Age [y:d:h:m:s]: 00:111:12:45:54
Block: 1174110 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 79477 RingCT/type: yes/0
Extra: 0136bec5a6e6131d482b08956ce6fecd48c9faff11a94d6037b96690fe12fac5d6021100000006007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c89bea03a19b3448f2055e2218f14da0072301f7391f1cf7d9908a60841a685c 0.600000000000 1660219 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": 1174120, "vin": [ { "gen": { "height": 1174110 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c89bea03a19b3448f2055e2218f14da0072301f7391f1cf7d9908a60841a685c" } } ], "extra": [ 1, 54, 190, 197, 166, 230, 19, 29, 72, 43, 8, 149, 108, 230, 254, 205, 72, 201, 250, 255, 17, 169, 77, 96, 55, 185, 102, 144, 254, 18, 250, 197, 214, 2, 17, 0, 0, 0, 6, 0, 127, 151, 138, 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