Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 90deeda21ffde0da937f25553d704e605f40faf8b666d068a31b869021a6974c

Tx prefix hash: f0321d41199c16baab387fc85d560771b68c6552443c853ca7a0d708cbf9d355
Tx public key: 9ee7e95e7b75c2bd016d9db277f77aa30554aaaca98d4650a3d13b0e701263c9
Timestamp: 1702228977 Timestamp [UCT]: 2023-12-10 17:22:57 Age [y:d:h:m:s]: 01:334:09:26:46
Block: 910222 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 497848 RingCT/type: yes/0
Extra: 019ee7e95e7b75c2bd016d9db277f77aa30554aaaca98d4650a3d13b0e701263c9021100000007e6d27f9c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4dd7105bdb140dea9a979d4f8f4e6a2d189f55984927da08aee7d9a8cbc907b9 0.600000000000 1367367 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": 910232, "vin": [ { "gen": { "height": 910222 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4dd7105bdb140dea9a979d4f8f4e6a2d189f55984927da08aee7d9a8cbc907b9" } } ], "extra": [ 1, 158, 231, 233, 94, 123, 117, 194, 189, 1, 109, 157, 178, 119, 247, 122, 163, 5, 84, 170, 172, 169, 141, 70, 80, 163, 209, 59, 14, 112, 18, 99, 201, 2, 17, 0, 0, 0, 7, 230, 210, 127, 156, 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