Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 13e42943db212a001a19ddc59ebc6283eebb516741216a578d02e1a2c20a01be

Tx prefix hash: 7f7d1aacc65e6e9ed80142d0877a28fb808e8af2499fefcd4873ab8d33f4e22c
Tx public key: 891f4f5bc442ec40bf8969cd382ee83254ff93054a7d54e0173b50e2d73643d5
Timestamp: 1718123546 Timestamp [UCT]: 2024-06-11 16:32:26 Age [y:d:h:m:s]: 00:335:11:22:34
Block: 1042009 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 239755 RingCT/type: yes/0
Extra: 01891f4f5bc442ec40bf8969cd382ee83254ff93054a7d54e0173b50e2d73643d502110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2aa1752eab1baf8d55e9ad72522005e922c33106b29a595ec063a4f87e13f530 0.600000000000 1510820 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": 1042019, "vin": [ { "gen": { "height": 1042009 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2aa1752eab1baf8d55e9ad72522005e922c33106b29a595ec063a4f87e13f530" } } ], "extra": [ 1, 137, 31, 79, 91, 196, 66, 236, 64, 191, 137, 105, 205, 56, 46, 232, 50, 84, 255, 147, 5, 74, 125, 84, 224, 23, 59, 80, 226, 215, 54, 67, 213, 2, 17, 0, 0, 0, 3, 82, 212, 126, 148, 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