Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bf3c5fd39404d07c38a1470c6ce39378f5a644b2de4bcc163b3cee361ac57f88

Tx prefix hash: f7c8bd0977da5e374b273864ffbb578f562b1b1edec5f6b185982d300357375b
Tx public key: 35a1df02f8afdc35f23901ca90dbbcd03f15d2f7356df7c25f39f06efb11954f
Timestamp: 1725039771 Timestamp [UCT]: 2024-08-30 17:42:51 Age [y:d:h:m:s]: 00:222:09:51:43
Block: 1099333 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 158819 RingCT/type: yes/0
Extra: 0135a1df02f8afdc35f23901ca90dbbcd03f15d2f7356df7c25f39f06efb11954f02110000000791e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 198de54a9841a847fd8473cf40c659e65907fa7d72bd569b3e04ccacfb8759f1 0.600000000000 1575294 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": 1099343, "vin": [ { "gen": { "height": 1099333 } } ], "vout": [ { "amount": 600000000, "target": { "key": "198de54a9841a847fd8473cf40c659e65907fa7d72bd569b3e04ccacfb8759f1" } } ], "extra": [ 1, 53, 161, 223, 2, 248, 175, 220, 53, 242, 57, 1, 202, 144, 219, 188, 208, 63, 21, 210, 247, 53, 109, 247, 194, 95, 57, 240, 110, 251, 17, 149, 79, 2, 17, 0, 0, 0, 7, 145, 225, 60, 4, 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