Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e7eeab0ceefeea3cfb5acc58f023e27c4a194f723a98094ab17846ec0d5dc3c6

Tx prefix hash: 1b02fb0fcfb0c1ec40d8599a5f2a2f6fd6cf27fcd7278ba1bb0da68e7fba1aab
Tx public key: 0e2c58e02f5c6e87ba7a00a5850405bf5233798d0bb3625bba5c9072c46df8c4
Timestamp: 1700952860 Timestamp [UCT]: 2023-11-25 22:54:20 Age [y:d:h:m:s]: 01:347:07:59:21
Block: 899639 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 507120 RingCT/type: yes/0
Extra: 010e2c58e02f5c6e87ba7a00a5850405bf5233798d0bb3625bba5c9072c46df8c402110000000533af99f4000000000000000000

1 output(s) for total of 0.641390494000 dcy

stealth address amount amount idx
00: ab864ba55e98528efdde7cf42f9b6e9536f074e9e291493d5bac1207024ef333 0.641390494000 1356098 of 0

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": 899649, "vin": [ { "gen": { "height": 899639 } } ], "vout": [ { "amount": 641390494, "target": { "key": "ab864ba55e98528efdde7cf42f9b6e9536f074e9e291493d5bac1207024ef333" } } ], "extra": [ 1, 14, 44, 88, 224, 47, 92, 110, 135, 186, 122, 0, 165, 133, 4, 5, 191, 82, 51, 121, 141, 11, 179, 98, 91, 186, 92, 144, 114, 196, 109, 248, 196, 2, 17, 0, 0, 0, 5, 51, 175, 153, 244, 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