Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0f5be503d0c7d0dd6cf78cd116ce509cd32feb176b02b308fde70237c43f37bb

Tx prefix hash: 243906b40b77c36db3c8d82e7207439c000b19f84d2599bfd3a8e5939cb3310a
Tx public key: 7bfc5e879a4e647c3d0db8c9f49daa3d4cf7c9cfb1be881622fa1685c8270e50
Timestamp: 1672660339 Timestamp [UCT]: 2023-01-02 11:52:19 Age [y:d:h:m:s]: 02:131:21:29:37
Block: 665949 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 615984 RingCT/type: yes/0
Extra: 017bfc5e879a4e647c3d0db8c9f49daa3d4cf7c9cfb1be881622fa1685c8270e50021100000001faf35c9c000000000000000000

1 output(s) for total of 3.814472406000 dcy

stealth address amount amount idx
00: b2cda7e8b4f899ad94a9ce637fccb0539ea6dcbdcee55a4c260970591b2e9fd1 3.814472406000 1107022 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": 665959, "vin": [ { "gen": { "height": 665949 } } ], "vout": [ { "amount": 3814472406, "target": { "key": "b2cda7e8b4f899ad94a9ce637fccb0539ea6dcbdcee55a4c260970591b2e9fd1" } } ], "extra": [ 1, 123, 252, 94, 135, 154, 78, 100, 124, 61, 13, 184, 201, 244, 157, 170, 61, 76, 247, 201, 207, 177, 190, 136, 22, 34, 250, 22, 133, 200, 39, 14, 80, 2, 17, 0, 0, 0, 1, 250, 243, 92, 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