Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4ffd21fd5f4883d40179623e1877ee102fce0b643e384485a5792c70714a9d24

Tx prefix hash: 98a3d03fe92c50368f6e93747fffe9eadeee78c1725db7458b98e8ae37c075d7
Tx public key: f9741daf5cbfc59e14fe99fbe01ed8c472b7e4a6cb4291752c33a7f4634752e0
Timestamp: 1726844605 Timestamp [UCT]: 2024-09-20 15:03:25 Age [y:d:h:m:s]: 00:155:13:42:33
Block: 1114299 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 110962 RingCT/type: yes/0
Extra: 01f9741daf5cbfc59e14fe99fbe01ed8c472b7e4a6cb4291752c33a7f4634752e002110000000791e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ead297ffbd35fffaf89af6e24b6cac2fe7286143e6754e22cf9d71a0d62e151a 0.600000000000 1594098 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": 1114309, "vin": [ { "gen": { "height": 1114299 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ead297ffbd35fffaf89af6e24b6cac2fe7286143e6754e22cf9d71a0d62e151a" } } ], "extra": [ 1, 249, 116, 29, 175, 92, 191, 197, 158, 20, 254, 153, 251, 224, 30, 216, 196, 114, 183, 228, 166, 203, 66, 145, 117, 44, 51, 167, 244, 99, 71, 82, 224, 2, 17, 0, 0, 0, 7, 145, 225, 60, 4, 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