Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 33c808505a9b92cf34e9c6c89d53ec1e1e5da5f45694f3d4ba13c87512ec3669

Tx prefix hash: 1745cd5ea303f0c35f444bb82305660cc56107ba562764a24114d5217c51a4c9
Tx public key: 8f5fa5296c83e068a5cf3ea4f79e44ae90efee7200b4514a7b9adc3822d6827b
Timestamp: 1697337874 Timestamp [UCT]: 2023-10-15 02:44:34 Age [y:d:h:m:s]: 01:099:04:55:41
Block: 869875 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 332116 RingCT/type: yes/0
Extra: 018f5fa5296c83e068a5cf3ea4f79e44ae90efee7200b4514a7b9adc3822d6827b02110000000175e3f0e9000000000000000000

1 output(s) for total of 0.804902081000 dcy

stealth address amount amount idx
00: 54e4871c41f0a291cd3abe8be448b4ccf64360b00fd75c27780b9eab4135a815 0.804902081000 1324740 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": 869885, "vin": [ { "gen": { "height": 869875 } } ], "vout": [ { "amount": 804902081, "target": { "key": "54e4871c41f0a291cd3abe8be448b4ccf64360b00fd75c27780b9eab4135a815" } } ], "extra": [ 1, 143, 95, 165, 41, 108, 131, 224, 104, 165, 207, 62, 164, 247, 158, 68, 174, 144, 239, 238, 114, 0, 180, 81, 74, 123, 154, 220, 56, 34, 214, 130, 123, 2, 17, 0, 0, 0, 1, 117, 227, 240, 233, 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