Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b23713afba11c7187fb1ac64d7c9df65336a2ed26f5e5d2505f0a0f61e7828a7

Tx prefix hash: d4ff46296aeb2045c8d32acdd475ca62073735135a68ad938c3425099b6f8278
Tx public key: 5d81868e7e7a61ca3028874815aee08fec6cc5381c227d0ae5104b4be7af6af5
Timestamp: 1723865519 Timestamp [UCT]: 2024-08-17 03:31:59 Age [y:d:h:m:s]: 00:223:06:57:32
Block: 1089605 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 159449 RingCT/type: yes/0
Extra: 015d81868e7e7a61ca3028874815aee08fec6cc5381c227d0ae5104b4be7af6af5021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b8d17f8eb907a446100b271914e0f4273f61ebc156d08f587b736a793b7afdca 0.600000000000 1564228 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": 1089615, "vin": [ { "gen": { "height": 1089605 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b8d17f8eb907a446100b271914e0f4273f61ebc156d08f587b736a793b7afdca" } } ], "extra": [ 1, 93, 129, 134, 142, 126, 122, 97, 202, 48, 40, 135, 72, 21, 174, 224, 143, 236, 108, 197, 56, 28, 34, 125, 10, 229, 16, 75, 75, 231, 175, 106, 245, 2, 17, 0, 0, 0, 2, 233, 20, 221, 21, 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