Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 48c1ff72c942a23fcf8340da1199af3319f3f3935c2d824ec9db9f44ff09a476

Tx prefix hash: aac953a7bfcf6624aa0785b1563b881551026a71593bce9773333710e599ed10
Tx public key: 5a4a613f4a900e956e3f595d71015cf0b6e0f8e40f1aaa8aa44974b35e905555
Timestamp: 1698095581 Timestamp [UCT]: 2023-10-23 21:13:01 Age [y:d:h:m:s]: 01:162:00:39:49
Block: 876163 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 376801 RingCT/type: yes/0
Extra: 015a4a613f4a900e956e3f595d71015cf0b6e0f8e40f1aaa8aa44974b35e90555502110000000375e3f0e9000000000000000000

1 output(s) for total of 0.767199457000 dcy

stealth address amount amount idx
00: a3b5683a62d06fb7b92719f053f27ee6c2457b5dd1422b1a3ea68d9b991be430 0.767199457000 1331473 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": 876173, "vin": [ { "gen": { "height": 876163 } } ], "vout": [ { "amount": 767199457, "target": { "key": "a3b5683a62d06fb7b92719f053f27ee6c2457b5dd1422b1a3ea68d9b991be430" } } ], "extra": [ 1, 90, 74, 97, 63, 74, 144, 14, 149, 110, 63, 89, 93, 113, 1, 92, 240, 182, 224, 248, 228, 15, 26, 170, 138, 164, 73, 116, 179, 94, 144, 85, 85, 2, 17, 0, 0, 0, 3, 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