Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0ae5c5dbe784a4e539234d2ccc0b007e11c84bf0cb938330c67c19b4e6306b4e

Tx prefix hash: 37f54e8228317e3bf9c4d430c9d9726bf6e1347a444f2f4a5e9c0e14e917182b
Tx public key: dacc789020f49068af5bac2b95e8d95ddfa3034055c3eaa34eae59b7a2ce26e6
Timestamp: 1734873982 Timestamp [UCT]: 2024-12-22 13:26:22 Age [y:d:h:m:s]: 00:098:11:14:53
Block: 1180774 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 70136 RingCT/type: yes/0
Extra: 01dacc789020f49068af5bac2b95e8d95ddfa3034055c3eaa34eae59b7a2ce26e60211000000051f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9d273b05057dc4d6f7d6d4cc2d8bf01fd0ba6496af39f4f0d8dca8dd3311a8eb 0.600000000000 1667187 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": 1180784, "vin": [ { "gen": { "height": 1180774 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9d273b05057dc4d6f7d6d4cc2d8bf01fd0ba6496af39f4f0d8dca8dd3311a8eb" } } ], "extra": [ 1, 218, 204, 120, 144, 32, 244, 144, 104, 175, 91, 172, 43, 149, 232, 217, 93, 223, 163, 3, 64, 85, 195, 234, 163, 78, 174, 89, 183, 162, 206, 38, 230, 2, 17, 0, 0, 0, 5, 31, 10, 83, 235, 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