Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8ffd1a80c7ba8e0843fc31fdb4e0d503bb3e662e6e3e8da0a540f374e714f972

Tx prefix hash: 473987e30b4f24d50330b036c9c35c059f02921a2f8ebb3a813872f4e01e4eba
Tx public key: e3301bdfa583fe6ec10c678dd06038318d84eaa943855bfdd1ee9e3dc6af30c0
Timestamp: 1733690057 Timestamp [UCT]: 2024-12-08 20:34:17 Age [y:d:h:m:s]: 00:141:15:05:47
Block: 1170971 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 101024 RingCT/type: yes/0
Extra: 01e3301bdfa583fe6ec10c678dd06038318d84eaa943855bfdd1ee9e3dc6af30c0021100000008007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4cbbceef20f17b2084814980eab3d94e59ed3215e6cf78d89af2d722111f5213 0.600000000000 1656706 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": 1170981, "vin": [ { "gen": { "height": 1170971 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4cbbceef20f17b2084814980eab3d94e59ed3215e6cf78d89af2d722111f5213" } } ], "extra": [ 1, 227, 48, 27, 223, 165, 131, 254, 110, 193, 12, 103, 141, 208, 96, 56, 49, 141, 132, 234, 169, 67, 133, 91, 253, 209, 238, 158, 61, 198, 175, 48, 192, 2, 17, 0, 0, 0, 8, 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